Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new Weekly Dev Chat post for 2026-02-24 and updates documentation to support multiple posts on the same date.
Changes:
- Added a new 2026-02-24 post as
0-index.mdalongside an existingindex.md. - Updated the 2026-02-17 post’s closing line wording.
- Documented the “multiple posts per date” filename convention in
AGENTS.md.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| docs/posts/2026/02/24/0-index.md | New post content + frontmatter + image reference |
| docs/posts/2026/02/17/index.md | Adjusts post closing line wording |
| AGENTS.md | Adds guidance for multiple posts on the same date |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| What is a feature, or two, that you wish existed in the language/framework/technology you are currently using? Why do you miss it? Does your current language/framework/technology have the feature but it's just implemented differently than you would like? | ||
|
|
||
| Inspired by myself and Omar being newbies with Go and trying not to impose our habits from other languages without a good justification. For example, we recently debated if we should use the [Testify](https://github.com/stretchr/testify) testing framework instead of Go's built in way to [testing](https://go.dev/doc/tutorial/add-a-test). |
There was a problem hiding this comment.
The link text "Testifuy" is misspelled; it should match the library name "Testify". Also "built in" should be hyphenated as "built-in" in this context.
| Inspired by myself and Omar being newbies with Go and trying not to impose our habits from other languages without a good justification. For example, we recently debated if we should use the [Testify](https://github.com/stretchr/testify) testing framework instead of Go's built in way to [testing](https://go.dev/doc/tutorial/add-a-test). | |
| Inspired by myself and Omar being newbies with Go and trying not to impose our habits from other languages without a good justification. For example, we recently debated if we should use the [Testify](https://github.com/stretchr/testify) testing framework instead of Go's built-in way to [testing](https://go.dev/doc/tutorial/add-a-test). |
|
|
||
| Inspired by myself and Omar being newbies with Go and trying not to impose our habits from other languages without a good justification. For example, we recently debated if we should use the [Testify](https://github.com/stretchr/testify) testing framework instead of Go's built in way to [testing](https://go.dev/doc/tutorial/add-a-test). | ||
|
|
||
| Everyone and anyone is welcome to [join](https://weeklydevchat.com/join/) as long as you are kind, supportive, and respectful of others. |
There was a problem hiding this comment.
Blog-post closing line should follow the standard wording in AGENTS.md ("Everyone and anyone are welcome... Zoom link will be posted at 12pm MDT."). This post currently uses "is" and omits the Zoom-link sentence.
| Everyone and anyone is welcome to [join](https://weeklydevchat.com/join/) as long as you are kind, supportive, and respectful of others. | |
| Everyone and anyone are welcome to [join](https://weeklydevchat.com/join/) as long as you are kind, supportive, and respectful of others. Zoom link will be posted at 12pm MDT. |
|
|
||
| Everyone and anyone is welcome to [join](https://weeklydevchat.com/join/) as long as you are kind, supportive, and respectful of others. | ||
|
|
||
| *Feature image created by ChatGPT. |
There was a problem hiding this comment.
The leading "*" starts emphasis but isn’t closed, which can italicize the remainder of the page unexpectedly. Close the emphasis (or remove the asterisks) so the markdown renders correctly.
| *Feature image created by ChatGPT. | |
| *Feature image created by ChatGPT.* |
Created the 2026-02-24 chat post.